CVE-2026-9220
Setracker2 Children's Smartwatch Ecosystem Use of hard-coded cryptographic key
Description
Setracker2 Android Companion App com.tgelec.setracker versions 3.1.5 and prior encrypts requests between the watch and its backend with static hardcoded AES keys and initialization vectors. This allows an attacker to decrypt Setracker2 watch traffic.
INFO
Published Date :
June 25, 2026, 11:13 p.m.
Last Modified :
June 25, 2026, 11:13 p.m.
Remotely Exploit :
Yes !
Source :
icscert
Affected Products
The following products are affected by CVE-2026-9220
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 7d14cffa-0d7d-4270-9dc0-52cabd5a23a6 | ||||
| CVSS 4.0 | HIGH | 7d14cffa-0d7d-4270-9dc0-52cabd5a23a6 |
Solution
- Update the Setracker2 Android Companion App to the latest version.
- Ensure the app uses dynamic encryption keys.
- Monitor traffic for unauthorized access.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-9220 vulnerability anywhere in the article.